feat: starting on the slimdown #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… convention camelCase. 3.create a template and type file
…teen-ai feat: added nineteen.ai llm & image support
…rt-evm-chain feat: plugin-nft-generation support evm chain
Galadriel docs and .env.example update
|
Based on the size data provided, here's a strategic approach to modularizing Eliza's dependencies into optional packages, focusing on the largest and most specialized modules: Media Processing Module (~300 MiB combined): [IVideoService] related dependencies: @ffmpeg-installer/ffmpeg (143.17 MiB) echogarden (152.54 MiB) @discordjs/opus (1.55 MiB) fluent-ffmpeg (1.58 MiB) AI/ML Module (~140 MiB combined): [Image Model Providers] and related services: @huggingface/transformers (96.94 MiB) onnxruntime-node (67.82 MiB) fastembed (31.13 MiB) langchain (13.00 MiB) Blockchain Integration Module (~80 MiB combined): Optional blockchain connectivity: web3-plugin-zksync (62.11 MiB) thirdweb (40.17 MiB) @solana/web3.js (3.93 MiB) ethers (3.92 MiB) Testing & Development Tools (~15 MiB combined): [Dependencies] that could be moved to devDependencies: vitest (2.32 MiB) typescript-eslint (1.36 MiB) jest (4.61 MiB) playwright (2.56 MiB) Platform Integration Module (~5 MiB combined): [Memory Manager] and platform-specific integrations: discord.js (3.45 MiB) @slack/web-api (1.32 MiB) @slack/events-api (1.09 MiB) This modularization would allow users to install only the features they need, significantly reducing the core package size and improving maintainability. |
…ding-column Fix/PostgreSQL Vector Embedding Validation (elizaOS#1687)
fix: fix multiversx-plugin
parent 1d5d74a author mike dupont <mike.dupont@introspector.local> 1736342650 -0500 committer mike dupont <mike.dupont@introspector.local> 1736435015 -0500 parent 1d5d74a author mike dupont <mike.dupont@introspector.local> 1736342650 -0500 committer mike dupont <mike.dupont@introspector.local> 1736435001 -0500 starting on the slimdown now it is building lint fix Update pnpm-lockfile-check.yml Update pr.yaml Update integrationTests.yaml Update image.yaml Update image.yaml Update pnpm-lockfile-check.yml Update smoke-tests.yml Update greetings.yml Update image.yaml Update image.yaml removing new packages adding docker hub
jmikedupont2
force-pushed
the
feature/reduce_modules_discord
branch
from
c55f34c to
be9bbb2
Compare
|
❌ The pnpm-lockfile is out of date. Please run |
added 2 commits
January 9, 2025 10:09
jmikedupont2
pushed a commit
that referenced
this pull request
Feb 4, 2025
jmikedupont2
pushed a commit
that referenced
this pull request
Mar 25, 2025
…0d0cfa4197985 parent 37158ce author mike dupont <mike.dupont@introspector.local> 1742666252 -0400 committer mike dupont <mike.dupont@introspector.local> 1742928635 -0400 # This is a combination of 2 commits. # This is the 1st commit message: parent 37158ce author mike dupont <mike.dupont@introspector.local> 1742666252 -0400 committer mike dupont <mike.dupont@introspector.local> 1742928469 -0400 rework of patch docker running starting debugging prettier update start of groq also adding untested vibe script that was ai generated for testing starting to load groq this should be automated via vibe update rebase wip update wip change to scripts moving the commands to scripts update branches fix the path of get secrets removing ips change to scripts moving the commands to scripts update branches fix the path of get secrets docker/2025/03/24 tech debt fix me agent name hack to use a different agent name on boot this branch name is hard coded into the user data so we will have to redeploy the template to switch it the docker image name is loaded from ssm start cli bugfixes aws rework of patch docker running starting debugging prettier update start of groq also adding untested vibe script that was ai generated for testing starting to load groq this should be automated via vibe update rebase wip update wip change to scripts moving the commands to scripts fix the path of get secrets add deps make voice works add an drag & drop option for env uploading padding more padding fixed add plugin command quickstart.md fixed add plugin command quickstart.md add redpill plugin update readme update package json minimal groq wip revert remove tide lots of strange type errors rebased feat: add partial agent update feat: make partial updates by navbars in char settings feat: restructure update by panels chore: remove debug logs chore: remove logs & fix avatar size chore: optimize logic for update fix: remove unused vars chore: ensure min req for agent start chore: remove unused function chore: enahnce settings update on agent chore: clean the code chore: temp disable usePlugins fix: env drag and drop update quick action links add thumbnails, update frontpage links cleanup core docs update sidebars and intro fetch latest news fix syntax highlighting update llms.txt files update analysis files update repomix configs update blog update blog post update post remove extra update config update news add new blog post add llms.txt generator workflow add mermaid / bun notes add new links at footer, add copy page button remove artifacts fix chatgpt link, and sidebars order add some svgs of worlds / rooms / entities removing ips change to scripts moving the commands to scripts update branches fix the path of get secrets # This is the commit message #2: tech debt fix me agent name hack to use a different agent name on boot this branch name is hard coded into the user data so we will have to redeploy the template to switch it the docker image name is loaded from ssm # This is the commit message #3: bugfixes aws
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
removing large packages
here are some of the larger packages
Hey Eliza.gg, which are the largest modules you would refactor into specialized elizas to reduce the core load?
Eliza : Based on the discussions in the community, there are a few key areas that could be refactored into specialized packages to make the core more lightweight and maintainable.
The main approach would be to start with @elizaos/core as the minimal installation [chat_2024-11-24]. This provides essential features while allowing users to opt-in to additional functionality they need.
Some key modules that could be separated:
Plugin System: The current plugin architecture could be modularized further, allowing users to only load the specific plugins they need [Plugin Configuration]
Platform-specific Clients: The Slack client and other platform integrations could be separated into their own packages [Slack Client]
Runtime Extensions: The modular runtime components could be split into "lego blocks" that users can add as needed [chat_2024-11-24]
This aligns with the community's suggestion to split packages for easier maintenance [chat_2024-12-01]. Users would have more control over their installation by only including the features they actually need, while keeping the core system stable and lightweight.
The configuration system could also be modernized by moving away from JSON to typed alternatives [chat_2024-11-24], which would improve type safety and developer experience.
15 sources
Issue elizaOS#878: chore(deps): update dependency @rollup/plugin-terser to v0.4.4
Issue elizaOS#1182: fix: Fix client.push issue and update README for Slack client verification
Issue elizaOS#692: chore(deps): pin dependencies
chat_2024-11-24
core
core
chat_2024-12-01
Issue elizaOS#770: chore(deps): update dependency @vitest/eslint-plugin to v1.1.13
chat_2024-12-07
Issue elizaOS#770: chore(deps): update dependency @vitest/eslint-plugin to v1.1.13
chat_2024-12-01
formatEvaluatorNames
chat_2024-11-24
Issue elizaOS#784: fix: When the plugins field in the .character.json file is configured with plugin name.
chat_2024-11-24
Based on the package sizes you've shared, here's a strategic approach to modularizing Eliza's dependencies into specialized packages:
Web3/Blockchain Module (~160MB combined):
thirdweb
web3-plugin-zksync
@lens-protocol/client
fuels
@anyone-protocol/anyone-client
AI/ML Module (~196MB combined):
@huggingface/transformers
onnxruntime-node
fastembed
node-llama-cpp
Media Processing Module (~295MB combined):
@ffmpeg-installer/ffmpeg
echogarden
Language Processing Module (~22MB):
kuromoji (Japanese tokenization)
Database Module (~38MB):
electric-sql/pglite
This modularization would allow users to install only the capabilities they need. For example:
A basic chatbot would only need the core package
A web3 agent would install the web3 module
A media processing agent would install the media module
An AI agent would install the AI/ML module
This aligns with the plugin architecture improvements [LlamaLocal Support] and would significantly reduce the base installation size for users who don't need all capabilities.
The core package could remain lean while providing a plugin system to easily add these specialized modules when needed [Image Model Provider].